SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Email client</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Email client</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">This article is about mail readers for Internet e-mail. For BBS mail readers, see <a href="Offline_reader" title="Offline reader">Offline reader</a>.</div>

<p>An <b>email client</b>, <b>email reader</b> or, more formally, <b>message user agent</b> (MUA) or <b>mail user agent</b> is a <a href="Computer_program" title="Computer program">computer program</a> used to access and manage a user's <a href="Email" title="Email">email</a>.

</p><p>A <a href="Web_app" class="mw-redirect" title="Web app">web application</a> which provides message management, composition, and reception functions may act as a <a href="Web_email" class="mw-redirect" title="Web email">web email client</a>, and a piece of <a href="Computer_hardware" title="Computer hardware">computer hardware</a> or software whose primary or most visible role is to work as an email client may also use the term.

</p>

<div class="mw-heading mw-heading2"><h2 id="Retrieving_messages_from_a_mailbox">Retrieving messages from a mailbox</h2></div>

<p>Like most client programs, an email client is only active when a user runs it. The common arrangement is for an email user (the client) to make an arrangement with a remote <a href="Mail_Transfer_Agent" class="mw-redirect" title="Mail Transfer Agent">Mail Transfer Agent</a>

(MTA) server for the receipt and storage of the client's emails. The MTA, using a suitable <a href="Mail_delivery_agent" class="mw-redirect" title="Mail delivery agent">mail delivery agent</a> (MDA), adds email messages to a client's storage as they arrive. The remote mail storage is referred to as the user's <a href="E-mail_Mailbox" class="mw-redirect" title="E-mail Mailbox">mailbox</a>. The default setting on many Unix systems is for the mail server to store formatted messages in <a href="Mbox" title="Mbox">mbox</a>, within the user's <a href="Home_directory" title="Home directory">home directory</a>. Of course, users of the system can log-in and run a mail client on the same computer that hosts their mailboxes; in which case, the server is not actually <i>remote</i>, other than in a generic sense.

</p><p>Emails are stored in the user's mailbox on the remote server until the user's email client requests them to be downloaded to the user's computer, or can otherwise access the user's mailbox on the possibly remote server. The email client can be set up to connect to multiple mailboxes at the same time and to request the download of emails either automatically, such as at pre-set intervals, or the request can be manually initiated by the user.

</p><p>A user's mailbox can be accessed in two dedicated ways. The <a href="Post_Office_Protocol" title="Post Office Protocol">Post Office Protocol</a> (POP) allows the user to download messages one at a time and only deletes them from the server after they have been successfully saved on local storage. It is possible to leave messages on the server to permit another client to access them. However, there is no provision for flagging a specific message as <i>seen</i>, <i>answered</i>, or <i>forwarded</i>, thus POP is not convenient for users who access the same mail from different machines.

</p><p>Alternatively, the <a href="Internet_Message_Access_Protocol" title="Internet Message Access Protocol">Internet Message Access Protocol</a> (IMAP) allows users to keep messages on the server, flagging them as appropriate. IMAP provides folders and sub-folders, which can be shared among different users with possibly different access rights. Typically, the <i>Sent</i>, <i>Drafts</i>, and <i>Trash</i> folders are created by default. IMAP features an <a href="IMAP_IDLE" title="IMAP IDLE"><i>idle</i> extension</a> for real-time updates, providing faster notification than polling, where long-lasting connections are feasible. See also the <a href="#Remote_messages">remote messages</a> section below.

</p><p>The <a href="JSON_Meta_Application_Protocol" title="JSON Meta Application Protocol">JSON Meta Application Protocol</a> (JMAP) is implemented using JSON APIs over HTTP and has been developed as an alternative to IMAP/SMTP.

</p><p>In addition, the mailbox storage can be accessed directly by programs running on the server or via <a href="Clustered_file_system#Shared-disk" title="Clustered file system">shared disks</a>. Direct access can be more efficient but is less portable as it depends on the mailbox format; it is used by some email clients, including some <a href="#Webmail">webmail</a> applications.

</p>

<div class="mw-heading mw-heading2"><h2 id="Message_composition">Message composition</h2></div>

<p>Email clients usually contain <a href="Graphical_user_interface" title="Graphical user interface">user interfaces</a> to display and edit text. Some applications permit the use of a program-external editor.

</p><p>The email clients will perform formatting according to <style data-mw-deduplicate="TemplateStyles:r1238218222">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5322">5322</a> for <a href="E-mail" class="mw-redirect" title="E-mail">headers</a> and <a href="E-mail" class="mw-redirect" title="E-mail">body</a>, and <a href="MIME" title="MIME">MIME</a> for non-textual content and attachments. Headers include the destination fields, <i>To</i>, <i>Cc</i> (short for <i>Carbon copy</i>), and <i>Bcc</i> (<i>Blind carbon copy</i>), and the originator fields <i>From</i> which is the message's author(s), <i>Sender</i> in case there are more authors, and <i>Reply-To</i> in case responses should be addressed to a different mailbox. To better assist the user with destination fields, many clients maintain one or more address books and/or are able to connect to an <a href="LDAP" class="mw-redirect" title="LDAP">LDAP</a> directory server. For originator fields, clients may support different identities.

</p><p>Client settings require the user's <i>real name</i> and <i>email address</i> for each user's identity, and possibly a list of LDAP servers.

</p>

<div class="mw-heading mw-heading2"><h2 id="Submitting_messages_to_a_server">Submitting messages to a server</h2></div>

<p>When a user wishes to create and send an email, the email client will handle the task. The email client is usually set up automatically to connect to the user's mail server, which is typically either a <a href="Mail_submission_agent" class="mw-redirect" title="Mail submission agent">MSA</a> or a <a href="Mail_transport_agent" class="mw-redirect" title="Mail transport agent">MTA</a>, two variations of the <a href="SMTP" class="mw-redirect" title="SMTP">SMTP</a> protocol. The email client which uses the SMTP protocol creates an authentication extension, which the mail server uses to authenticate the sender. This method eases modularity and nomadic computing. The older method was for the mail server to recognize the client's IP address, e.g. because the client is on the same machine and uses internal address 127.0.0.1, or because the client's IP address is controlled by the same <a href="Internet_service_provider" title="Internet service provider">Internet service provider</a> that provides both Internet access and mail services.

</p><p>Client settings require the name or IP address of the preferred <i>outgoing mail server</i>, the <i>port number</i>, and the <i>user name</i> and <i>password</i> for authentication, if any. The following ports are used for email submission:

</p><p>- <b>Port 465</b> – The officially designated port for mail submission using <a href="Transport_Layer_Security" title="Transport Layer Security">TLS</a> from the start of the connection (Implicit TLS), as per <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc8314.html">RFC 8314</a>. Since encryption is enforced from the beginning, it eliminates the risk of downgrade attacks or MITM (Man-in-the-Middle) attacks that could strip away encryption.

</p><p>- <b>Port 587</b> – Commonly used for mail submission with support for <a href="STARTTLS" class="mw-redirect" title="STARTTLS">STARTTLS</a>, allowing the connection to be optionally upgraded to TLS. However, if a MITM attacker interferes with the STARTTLS command, the connection may remain unencrypted, making it less secure than implicit TLS on port 465.

</p><p>Port 25, originally intended for message relay between MTAs, is <b>not for client message submission</b> and is often blocked by ISPs to prevent spam.

</p>

<div class="mw-heading mw-heading2"><h2 id="Encryption">Encryption</h2></div>

<p>With no encryption, much like for postcards, email activity is plainly visible by any occasional eavesdropper. <a href="Email_encryption" title="Email encryption">Email encryption</a> enables privacy to be safeguarded by encrypting the mail sessions, the body of the message, or both. Without it, anyone with network access and the right tools can monitor email and obtain login passwords. Examples of concern include the government <a href="Censorship" title="Censorship">censorship</a> and <a href="Surveillance" title="Surveillance">surveillance</a> and fellow wireless network users such as at an <a href="Internet_cafe" class="mw-redirect" title="Internet cafe">Internet cafe</a>.

</p><p>All relevant email protocols have an option to encrypt the whole session, to prevent a user's <i>name</i> and <i>password</i> from being <a href="Packet_sniffer" class="mw-redirect" title="Packet sniffer">sniffed</a>. They are strongly suggested for nomadic users and whenever the <a href="Internet_access_provider" class="mw-redirect" title="Internet access provider">Internet access provider</a> is not trusted.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> When sending mail, users can only control encryption at the first hop from a client to its configured <i>outgoing mail server</i>. At any further hop, messages may be transmitted with or without encryption, depending solely on the general configuration of the transmitting server and the capabilities of the receiving one.

</p><p>Encrypted mail sessions deliver messages in their original format, i.e. plain text or encrypted body, on a user's local mailbox and on the destination server's. The latter server is operated by an <a href="Email_hosting_service" title="Email hosting service">email hosting service</a> provider, possibly a different entity than the Internet <i>access</i> provider currently at hand.

</p><p>Encrypting an email retrieval session with, e.g., SSL, can protect both parts (authentication, and message transfer) of the session.<sup id="cite_ref-sill-security_2-0" class="reference"><a href="#cite_note-sill-security-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup>

</p><p>Alternatively, if the user has <a href="Secure_Shell" title="Secure Shell">SSH</a> access to their mail server, they can use SSH <a href="Port_forwarding" title="Port forwarding">port forwarding</a> to create an encrypted tunnel over which to retrieve their emails.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Encryption_of_the_message_body">Encryption of the message body</h3></div>

<p>There are two main models for managing cryptographic keys. <a href="S/MIME" title="S/MIME">S/MIME</a> employs a model based on a trusted <a href="Certificate_authority" title="Certificate authority">certificate authority</a> (CA) that signs users' public keys. <a href="OpenPGP" class="mw-redirect" title="OpenPGP">OpenPGP</a> employs a somewhat more flexible <i><a href="Web_of_trust" title="Web of trust">web of trust</a></i> mechanism that allows users to sign one another's public keys. OpenPGP is also more flexible in the format of the messages, in that it still supports plain message encryption and signing as they used to work before <a href="MIME" title="MIME">MIME</a> standardization.

</p><p>In both cases, only the message body is encrypted. Header fields, including originator, recipients, and often subject, remain in plain text.

</p>

<div class="mw-heading mw-heading2"><h2 id="Webmail">Webmail</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Webmail" title="Webmail">Webmail</a></div>

<p>In addition to email clients running on a desktop computer, there are those hosted remotely, either as part of a remote UNIX installation accessible by <a href="Telnet" title="Telnet">telnet</a> (i.e. a <a href="Shell_account" title="Shell account">shell account</a>), or hosted on the <a href="World_Wide_Web" title="World Wide Web">Web</a>. Both of these approaches have several advantages: they share an ability to send and receive email away from the user's normal base using a <a href="Web_browser" title="Web browser">web browser</a> or telnet client, thus eliminating the need to install a dedicated email client on the user's device.

</p><p>Some websites are dedicated to providing email services, and many <a href="Internet_service_provider" title="Internet service provider">Internet service providers</a> provide webmail services as part of their Internet service package. The main limitations of webmail are that user interactions are subject to the website's operating system and the general inability to download email messages and compose or work on the messages offline, although there are software packages that can integrate parts of the webmail functionality into the OS (e.g. creating messages directly from third party applications via <a href="MAPI" title="MAPI">MAPI</a>).

</p><p>Like IMAP and MAPI, webmail provides for email messages to remain on the mail server. See <a href="#Remote_messages">next section</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Remote_messages"> Remote messages</h2></div>

<p>POP3 has an option to leave messages on the server. By contrast, both IMAP and webmail keep messages on the server as their method of operating, albeit users can make local copies as they like. Keeping messages on the server has advantages and disadvantages.<sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading3"><h3 id="Advantages">Advantages</h3></div>

<ul><li>Messages can be accessed from various computers or mobile devices at different locations, using different clients.</li>

<li>Some kind of backup is usually provided by the server.</li></ul>

<div class="mw-heading mw-heading3"><h3 id="Disadvantages">Disadvantages</h3></div>

<ul><li>With limited bandwidth, access to long messages can be lengthy, unless the email client caches a local copy.</li>

<li>There may be privacy concerns since messages that stay on the server at all times have more chances to be casually accessed by IT personnel, unless <a href="End-to-end_encryption" title="End-to-end encryption">end-to-end encryption</a> is used.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Protocols">Protocols</h2></div>

<p>Popular protocols for retrieving mail include <a href="POP3" class="mw-redirect" title="POP3">POP3</a> and <a href="IMAP4" class="mw-redirect" title="IMAP4">IMAP4</a>. Sending mail is usually done using the <a href="SMTP" class="mw-redirect" title="SMTP">SMTP</a> protocol.

</p><p>Another important standard supported by most email clients is <a href="MIME" title="MIME">MIME</a>, which is used to send <a href="Binary_file" title="Binary file">binary file</a> <a href="Email_attachment" title="Email attachment">email attachments</a>. Attachments are files that are not part of the email proper but are sent with the email.

</p><p>Most email clients use a <i>User-Agent</i><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> <a href="Header_(computing)" title="Header (computing)">header field</a> to identify the software used to send the message. This header field is defined for Netnews, but not-for e-mail, and, as such, is non-standard<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup> in e-mail headers.

</p><p><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc6409">6409</a>, <i>Message Submission for Mail</i>, details the role of the <a href="Mail_submission_agent" class="mw-redirect" title="Mail submission agent">Mail submission agent</a>.

</p><p><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5068">5068</a>, <i>Email Submission Operations: Access and Accountability Requirements</i>, provides a survey of the concepts of MTA, MSA, MDA, and MUA. It mentions that "<i> Access Providers MUST NOT block users from accessing the external Internet using the SUBMISSION port 587</i>" and that "<i>MUAs SHOULD use the SUBMISSION port for message submission.</i>"

</p><p><a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc5965">5965</a>, <i>An Extensible Format for Email Feedback Reports</i>, provides "an extensible format and MIME type that may be used by mail operators to report feedback about received email to other parties."

</p>

<div class="mw-heading mw-heading3"><h3 id="Port_numbers">Port numbers</h3></div>

<p>Email servers and clients by convention use the <a href="List_of_TCP_and_UDP_port_numbers" title="List of TCP and UDP port numbers">TCP port numbers</a> in the following table. For MSA, IMAP and POP3, the table reports also the labels that a client can use to query the <a href="SRV_record" title="SRV record">SRV records</a> and discover both the host name and the port number of the corresponding service.<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup>

</p>

<th>Protocol

</th>

<th>Use

</th>

<th>Plain text or <br>encrypt sessions

</th>

<th>Plain text <br>sessions only

</th>

<th>Encrypt sessions <br>only

</th></tr>

<tr>

</td>

<td>incoming mail

</td>

<td style="text-align: right;">110 <br>_pop3._tcp

</td>

<td>

</td>

<td style="text-align: right;">995 <br>_pop3s._tcp

</td></tr>

<tr>

</td>

<td>incoming mail

</td>

<td style="text-align: right;">143 <br>_imap._tcp

</td>

<td>

</td>

<td style="text-align: right;">993 <br>_imaps._tcp

</td></tr>

<tr>

</td>

<td>outgoing mail

</td>

<td style="text-align: right;">25

</td>

<td>

</td>

<td style="text-align: right;">587

</td></tr>

<tr>

</td>

<td>outgoing mail

</td>

<td style="text-align: right;">587 <br>_submission._tcp

</td>

<td>

</td>

<td style="text-align: right;">465<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> <br>_submissions._tcp

</td></tr>

<tr>

</td>

<td>webmail

</td>

<td>

</td>

<td style="text-align: right;">80

</td>

<td style="text-align: right;">443

</td></tr></tbody></table>

<p>While webmail obeys the earlier HTTP disposition of having separate ports for encrypt and plain text sessions, mail protocols use the <a href="STARTTLS" class="mw-redirect" title="STARTTLS">STARTTLS</a> technique, thereby allowing encryption to start on an already established TCP connection. While <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc2595">2595</a> used to discourage the use of the previously established ports 995 and 993, <a href="RFC_(identifier)" class="mw-redirect" title="RFC (identifier)">RFC</a> <a rel="nofollow" class="external text" href="https://www.rfc-editor.org/rfc/rfc8314">8314</a> promotes the use of implicit <a href="Transport_Layer_Security" title="Transport Layer Security">TLS</a> when available.

</p>

<div class="mw-heading mw-heading3"><h3 id="Proprietary_client_protocols">Proprietary client protocols</h3></div>

<p><a href="Microsoft" title="Microsoft">Microsoft</a> mail systems use the <a href="Proprietary_software" title="Proprietary software">proprietary</a> <a href="Messaging_Application_Programming_Interface" class="mw-redirect" title="Messaging Application Programming Interface">Messaging Application Programming Interface</a> (MAPI) in client applications, such as <a href="Microsoft_Outlook" title="Microsoft Outlook">Microsoft Outlook</a>, to access <a href="Microsoft_Exchange_Server" title="Microsoft Exchange Server">Microsoft Exchange</a> electronic mail servers.

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Look up <i><b><a href="https://en.wiktionary.org/wiki/Special:Search/email_client" class="extiw external" title="wiktionary:Special:Search/email client">email client</a></b></i> in Wiktionary, the free dictionary.</div></div>

</div>

<ul><li><a href="Comparison_of_email_clients" title="Comparison of email clients">Comparison of email clients</a></li>

<li><a href="Message_submission_agent" title="Message submission agent">Message submission agent</a> (MSA)</li>

<li><a href="Mailto" title="Mailto">Mailto</a></li>

<li><a href="Message_delivery_agent" title="Message delivery agent">Message delivery agent</a> (MDA)</li>

<li><a href="Message_transfer_agent" title="Message transfer agent">Message transfer agent</a> (MTA)</li>

<li><a href="Simple_Mail_Transfer_Protocol" title="Simple Mail Transfer Protocol">Simple Mail Transfer Protocol</a></li>

<li><a href="Text-based_email_client" title="Text-based email client">Text-based email client</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

<li id="cite_note-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-1">^</a></b></span> <span class="reference-text"><cite id="CITEREFC._HutzlerD._CrockerP._ResnickE._Allman2007" class="citation cs1">C. Hutzler; D. Crocker; P. Resnick; E. Allman; T. Finch (November 2007). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5068#section-5">"Message Submission Authentication/Authorization Technologies"</a>. <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5068"><i>Email Submission Operations: Access and Accountability Requirements</i></a>. <a href="IETF" class="mw-redirect" title="IETF">IETF</a>. sec. 5. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC5068">10.17487/RFC5068</a></span>. BCP 134. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5068">5068</a><span class="reference-accessdate">. Retrieved <span class="nowrap">24 August</span> 2011</span>. <q>This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.</q></cite> </span>

</li>

<li id="cite_note-sill-security-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-sill-security_2-0">^</a></b></span> <span class="reference-text"><a href="#CITEREFSill2003">Sill 2003</a>, p. 353: "Like SMTP, POP3 is unencrypted. Unlike SMTP, however, it needs authentication: Users have to identify themselves and prove they're who they claim to be. Unfortunately, the authentication usually consists of presenting a username and a password known only to the user and the POP3 server. Because the POP3 dialogue is unencrypted, an eavesdropper can obtain a user's username and password and reuse them to access the user's mailbox. So, plain POP3 exposes the contents of the mail messages the user retrieves, and it exposes their username and password, which can then be reused by someone else.<br>Wrapping the POP3 dialogue with transport-layer security such as SSL solves both of these problems. Because SSL-wrapped POP3 sessions are encrypted from beginning to end, no messages, usernames, or passwords are exposed in cleartext.<br>The optional POP3 command, <code>APOP</code>, replaces the standard <code>USER/PASS</code> authentication with a challenge-response authentication mechanism. This solves the problem of the disclosure of reusable passwords, but does nothing to prevent eavesdroppers from reading users' mail messages as they're being retrieved."</span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text"><cite class="citation cs1"><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7817"><i>Updated Transport Layer Security (TLS) Server Identity Check Procedure for Email-Related Protocols</i></a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC7817">10.17487/RFC7817</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc7817">7817</a>.</cite></span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text"><cite id="CITEREFFlickenger2003" class="citation book cs1">Flickenger, Rob (2003). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/linuxserverhacks00flic/page/146"><i>Linux Server Hacks: 100 Industrial-Strength Tips & Tools</i></a></span>. <a href="O'Reilly_Media" title="O'Reilly Media">O'Reilly Media</a>. p. <a rel="nofollow" class="external text" href="https://archive.org/details/linuxserverhacks00flic/page/146">146</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0596004613</bdi>. <q>In addition to providing remote shell access and command execution, OpenSSH can forward arbitrary TCP ports to the other end of your connection. This can be very handy for protecting email, web, or any other traffic you need to keep private (at least, all the way to the other end of the tunnel).<br><i>ssh</i> accomplishes local forwarding by binding to a local port, performing encryption, sending the encrypted data to the remote end of the <i>ssh</i> connection, then decrypting it and sending it to the remote host and port you specify. Start an <i>ssh</i> tunnel with the <i>-L</i> switch (short for Local):<br><code>root@laptop:~# <b>ssh -f -N -L110:<i>mailhost</i>:110 -l <i>user</i> <i>mailhost</i></b></code><br>Naturally, substitute <i>user</i> with your username, and <i>mailhost</i> with your mail server's name or IP address. Note that you will have to be root on the laptop for this example since you'll be binding to a privileged port (110, the POP port). You should also disable any locally running POP daemon (look in <i>/etc/inetd.conf</i>) or it will get in the way.<br>Now to encrypt all of your POP traffic, configure your mail client to connect to localhost port 110. It will happily talk to mailhost as if it were connected directly, except that the entire conversation will be encrypted.</q></cite></span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text"><cite class="citation web cs1 cs1-prop-unfit"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20100430153051/http://itservices.stanford.edu/service/emailcalendar/email/imap/rightforme">"Is IMAP Right for Me?"</a>. <i>IT Services</i>. <a href="Stanford_University" title="Stanford University">Stanford University</a>. 4 March 2010. Archived from the original on 30 April 2010<span class="reference-accessdate">. Retrieved <span class="nowrap">14 April</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text"><cite class="citation cs1"><a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5536#section-3.2.13">"User-Agent"</a>. <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5536"><i>Netnews Article Format</i></a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. November 2009. sec. 3.2.13. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC5536">10.17487/RFC5536</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc5536">5536</a>. <q>Some of this information has previously been sent in non-standardized header fields such as X-Newsreader, X-Mailer, X-Posting-Agent, X-Http-User-Agent, and others</q></cite></span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><cite id="CITEREFJ._Palme1997" class="citation cs1">J. Palme (February 1997). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2076#section-2">"Use of gatewaying headers"</a>. <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2076"><i>Common Internet Message Headers</i></a>. sec. 2. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC2076">10.17487/RFC2076</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc2076">2076</a><span class="reference-accessdate">. Retrieved <span class="nowrap">May 11,</span> 2015</span>. <q>Headers defined only in RFC 1036 for use in Usenet News sometimes appear in mail messages, either because the messages have been gatewayed from Usenet News to e-mail, or because the messages were written in combined clients supporting both e-mail and Usenet News in the same client. These headers are not standardized for use in Internet e-mail and should be handled with caution by e-mail agents.</q></cite></span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite id="CITEREFCyrus_Daboo2011" class="citation cs1">Cyrus Daboo (March 2011). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6186"><i>Use of SRV Records for Locating Email Submission/Access Services</i></a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC6186">10.17487/RFC6186</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc6186">6186</a><span class="reference-accessdate">. Retrieved <span class="nowrap">17 April</span> 2013</span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFKeith_MooreChris_Newman2018" class="citation cs1">Keith Moore; Chris Newman (January 2018). <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8314"><i>Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access</i></a>. <a href="Internet_Engineering_Task_Force" title="Internet Engineering Task Force">IETF</a>. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.17487%2FRFC8314">10.17487/RFC8314</a></span>. <a href="Request_for_Comments" title="Request for Comments">RFC</a> <a rel="nofollow" class="external text" href="https://datatracker.ietf.org/doc/html/rfc8314">8314</a><span class="reference-accessdate">. Retrieved <span class="nowrap">12 February</span> 2018</span>.</cite></span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="Bibliography">Bibliography</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .refbegin{margin-bottom:0.5em}.mw-parser-output .refbegin-hanging-indents>ul{margin-left:0}.mw-parser-output .refbegin-hanging-indents>ul>li{margin-left:0;padding-left:3.2em;text-indent:-3.2em}.mw-parser-output .refbegin-hanging-indents ul,.mw-parser-output .refbegin-hanging-indents ul li{list-style:none}@media(max-width:720px){.mw-parser-output .refbegin-hanging-indents>ul>li{padding-left:1.6em;text-indent:-1.6em}}.mw-parser-output .refbegin-columns{margin-top:0.3em}.mw-parser-output .refbegin-columns ul{margin-top:0}.mw-parser-output .refbegin-columns li{page-break-inside:avoid;break-inside:avoid-column}@media screen{.mw-parser-output .refbegin{font-size:90%}}

/* end https://en.wikipedia.org/ */

</style><div class="refbegin" style="">

<ul><li><cite id="CITEREFSill2003" class="citation book cs1">Sill, Dave (2003). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=yUUnCgAAQBAJ&q=%22uw+imap%22&pg=PA348"><i>The qmail Handbook</i></a>. <a href="Apress" class="mw-redirect" title="Apress">Apress</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781430211341</bdi>.</cite></li>

<li><cite id="CITEREFPartridge2008" class="citation journal cs1">Partridge, Craig (April–June 2008). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20110512165437/http://www.ir.bbn.com/~craig/email.pdf">"The Technical Development of Internet Email"</a> <span class="cs1-format">(PDF)</span>. <i>IEEE Annals of the History of Computing</i>. <b>30</b> (2): <span class="nowrap">3–</span>29. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2Fmahc.2008.32">10.1109/mahc.2008.32</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/1934-1547">1934-1547</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:206442868">206442868</a>. Archived from <a rel="nofollow" class="external text" href="http://www.ir.bbn.com/~craig/email.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-05-12.</cite></li></ul>

</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Email_clients158" style="padding:3px"><table class="nowraplinks hlist mw-collapsible mw-collapsed navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Email_clients158" style="font-size:114%;margin:0 4em"></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Free software</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Current</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Alpine_(email_client)" title="Alpine (email client)">Alpine</a></li>

<li><a href="Balsa_(email_client)" title="Balsa (email client)">Balsa</a></li>

<li><a href="Citadel/UX" title="Citadel/UX">Citadel/UX</a></li>

<li><a href="Claws_Mail" title="Claws Mail">Claws Mail</a></li>

<li><a href="Cleancode_eMail" title="Cleancode eMail">Cleancode eMail</a></li>

<li><a href="GNOME_Evolution" title="GNOME Evolution">Evolution</a></li>

<li><a href="Fetchmail" title="Fetchmail">fetchmail</a></li>

<li><a href="Geary_(e-mail_client)" title="Geary (e-mail client)">Geary</a></li>

<li><a href="Getmail" title="Getmail">getmail</a></li>

<li><a href="GNUMail" title="GNUMail">GNUMail</a></li>

<li><a href="Gnuzilla" class="mw-redirect" title="Gnuzilla">Gnuzilla</a></li>

<li><a href="Kontact" title="Kontact">KMail</a></li>

<li><a href="Mahogany_(email_client)" title="Mahogany (email client)">Mahogany</a></li>

<li><a href="Mailpile" title="Mailpile">Mailpile</a></li>

<li><a href="Mailx" title="Mailx">Mailx</a></li>

<li><a href="Heirloom_Project" title="Heirloom Project">Mailx (Heirloom Project)</a></li>

<li><a href="Modest_(email_client)" title="Modest (email client)">Modest</a></li>

<li><a href="Mozilla_Thunderbird" title="Mozilla Thunderbird">Mozilla Thunderbird</a></li>

<li><a href="Mulberry_(email_client)" title="Mulberry (email client)">Mulberry</a></li>

<li><a href="OfflineIMAP" title="OfflineIMAP">OfflineIMAP</a></li>

<li><a href="Roundcube" title="Roundcube">Roundcube</a></li>

<li><a href="SeaMonkey" title="SeaMonkey">SeaMonkey</a></li>

<li><a href="SquirrelMail" title="SquirrelMail">SquirrelMail</a></li>

<li><a href="Sylpheed" title="Sylpheed">Sylpheed</a></li>

<li><a href="Trojit%C3%A1" title="Trojitá">Trojitá</a></li>

<li><a href="Zimbra" title="Zimbra">Zimbra</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Discontinued</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Arachne_(web_browser)" title="Arachne (web browser)">Arachne</a></li>

<li><a href="Beonex_Communicator" title="Beonex Communicator">Beonex Communicator</a></li>

<li><a href="BlitzMail" title="BlitzMail">BlitzMail</a></li>

<li><a href="Classilla" title="Classilla">Classilla</a></li>

<li><a href="Columbia_MM" title="Columbia MM">Columbia MM</a></li>

<li><a href="Pale_Moon_(web_browser)" class="mw-redirect" title="Pale Moon (web browser)">FossaMail</a></li>

<li><a href="Mailody" title="Mailody">Mailody</a></li>

<li><a href="Mozilla_Mail_%26_Newsgroups" title="Mozilla Mail & Newsgroups">Mozilla Mail & Newsgroups</a></li>

<li><a href="Nylas_N1" class="mw-redirect" title="Nylas N1">Nylas N1</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Proprietary</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Freeware/Freemium</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="EM_Client" title="EM Client">eM Client</a></li>

<li><a href="EmailTray" title="EmailTray">EmailTray</a></li>

<li><a href="Foxmail" title="Foxmail">Foxmail</a></li>

<li><a href="Scribe_Mail" title="Scribe Mail">i.Scribe</a></li>

<li><a href="Mailbird" title="Mailbird">Mailbird</a></li>

<li><a href="Spark_(application)" class="mw-redirect" title="Spark (application)">Spark</a></li>

<li><a href="Spike_(application)" title="Spike (application)">Spike</a></li>

<li><a href="TouchMail" title="TouchMail">TouchMail</a></li>

<li><a href="Vivaldi_(web_browser)" title="Vivaldi (web browser)">Vivaldi Mail</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Retail</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Bloomba" title="Bloomba">Bloomba/WordPerfect Mail</a></li>

<li><a href="Newton_(app)" class="mw-redirect" title="Newton (app)">Newton</a></li>

<li><a href="HCL_Domino" class="mw-redirect" title="HCL Domino">HCL Domino</a></li>

<li><a href="Scribe_Mail" title="Scribe Mail">InScribe</a></li>

<li><a href="Apple_Mail" title="Apple Mail">Apple Mail</a></li>

<li><a href="Mail_(Windows)" title="Mail (Windows)">Mail (Windows)</a></li>

<li><a href="Microsoft_Outlook" title="Microsoft Outlook">Microsoft Outlook</a></li>

<li><a href="Outlook_for_Windows" title="Outlook for Windows">Outlook for Windows</a></li>

<li><a href="GroupWise" title="GroupWise">Novell GroupWise</a></li>

<li><a href="Airmail_(email_client)" title="Airmail (email client)">Airmail</a></li>

<li><a href="Postbox_(email_client)" title="Postbox (email client)">Postbox</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Shareware</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Becky!" title="Becky!">Becky!</a></li>

<li><a href="Fort%C3%A9_Agent" title="Forté Agent">Forté Agent</a></li>

<li><a href="GyazMail" title="GyazMail">GyazMail</a></li>

<li><a href="Samsung_Email" class="mw-redirect" title="Samsung Email">Samsung Email</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Donationware</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Pegasus_Mail" title="Pegasus Mail">Pegasus Mail</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Discontinued</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Claris_Emailer" title="Claris Emailer">Claris Emailer</a></li>

<li><a href="Courier_(email_client)" title="Courier (email client)">Courier</a></li>

<li><a href="Cyberdog" title="Cyberdog">Cyberdog</a></li>

<li><a href="Cyberjack" title="Cyberjack">Cyberjack</a></li>

<li><a href="Embrowser" class="mw-redirect" title="Embrowser">Embrowser</a></li>

<li><a href="Eudora_(email_client)" title="Eudora (email client)">Eudora</a></li>

<li><a href="Mailbox_(application)" title="Mailbox (application)">Mailbox</a></li>

<li><a href="Microsoft_Entourage" title="Microsoft Entourage">Microsoft Entourage</a></li>

<li><a href="Microsoft_Internet_Mail_and_News" class="mw-redirect" title="Microsoft Internet Mail and News">Microsoft Internet Mail and News</a></li>

<li><a href="Microsoft_Mail" title="Microsoft Mail">Microsoft Mail</a></li>

<li><a href="Minnesota_Internet_Users_Essential_Tool" title="Minnesota Internet Users Essential Tool">MINUET</a></li>

<li><a href="Netscape_Mail_%26_Newsgroups" title="Netscape Mail & Newsgroups">Netscape Mail</a></li>

<li><a href="Netscape_Messenger_9" class="mw-redirect" title="Netscape Messenger 9">Netscape Messenger 9</a></li>

<li><a href="NeXTMail" class="mw-redirect" title="NeXTMail">NeXTMail</a></li>

<li><a href="Outlook_Express" title="Outlook Express">Outlook Express</a></li>

<li><a href="Pocomail" title="Pocomail">Pocomail</a></li>

<li><a href="POPmail" class="mw-redirect" title="POPmail">POPmail</a></li>

<li><a href="Sparrow_(email_client)" title="Sparrow (email client)">Sparrow</a></li>

<li><a href="Turnpike_(software)" title="Turnpike (software)">Turnpike</a></li>

<li><a href="WebSpyder" class="mw-redirect" title="WebSpyder">WebSpyder</a></li>

<li><a href="Windows_Live_Mail" title="Windows Live Mail">Windows Live Mail</a></li>

<li><a href="Windows_Messaging" title="Windows Messaging">Windows Messaging</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related technologies</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Related topics</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Email" title="Email">Email</a></li>

<li><a href="Unicode_and_email" title="Unicode and email">Unicode and email</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2" style="font-weight:bold;"><div>

<ul><li>Category</li>

<li><a href="Comparison_of_email_clients" title="Comparison of email clients">Comparison</a></li></ul>

</div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-01" href="https://en.wikipedia.org/wiki/?title=Email_client&oldid=1288333769">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>